Embedded vs. Autonomous Workflow – Putting Paradigms into Perspective

This paper distinguishes, at a high level, the differences between the architectures of workflow management systems. Its main function is to clarify the segmentation between autonomous and embedded workflow deployments. Workflow is the automation of a business process, in whole or in part, during which documents, information, or tasks are passed from one participant to another for action, according to a software representation of the process logic, the workflow model. A workflow management system defines, creates and manages the execution of workflows, through the use of software, running on one or more workflow engines, which is able to interpret the process definition, interact with workflow participants, and, where required, invoke the use of information technology (IT) tools and applications. A workflow engine provides the run-time execution of business processes. Engines can be embedded within other applications or they can be deployed as independent applications inter-operating with other applications. Some engines can be deployed in either mode. It is claimed that some application components, which deal with rules or exceptions, are in fact workflow engines, whilst they do not display most features that identify common workflow features. With the advent of new requirements for workflow engines to inter-operate for tasks such as Supply Chain Management, it is important for the market to be able to distinguish between inaccessible rulesbased application components, and workflow engines, be they embedded or not.